OBSDOCS-1860: Release Notes (RNs) for OpenShift Logging 6.3 Release #96021

theashiot · 2025-07-11T17:07:41Z

Version(s): 6.3

Issue: OBSDOCS-1860

Link to docs preview: https://96021--ocpdocs-pr.netlify.app/openshift-logging/latest/about/logging-release-notes.html

QE review:

QE has approved this change.

Additional information:

openshift-ci-robot · 2025-07-11T17:07:46Z

@theashiot: This pull request references OBSDOCS-1860 which is a valid jira issue.

In response to this:

Version(s): 6.3

Issue: OBSDOCS-1860

Link to docs preview:

QE review:

QE has approved this change.

Additional information:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci · 2025-07-11T17:07:48Z

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

theashiot · 2025-07-11T17:08:02Z

/test all

ocpdocs-previewbot · 2025-07-11T17:16:22Z

🤖 Wed Jul 16 12:14:08 - Prow CI generated the docs preview:

https://96021--ocpdocs-pr.netlify.app/openshift-logging/latest/about/logging-release-notes.html

theashiot · 2025-07-11T17:34:00Z

/test all

openshift-ci-robot · 2025-07-11T19:24:46Z

@theashiot: This pull request references OBSDOCS-1860 which is a valid jira issue.

In response to this:

Version(s): 6.3

Issue: OBSDOCS-1860

Link to docs preview: https://96021--ocpdocs-pr.netlify.app/openshift-logging/latest/about/logging-release-notes.html

QE review:

QE has approved this change.

Additional information:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

theashiot · 2025-07-14T17:04:59Z

/label peer-review-needed

brendan-daly-red-hat · 2025-07-15T11:21:39Z

/label peer-review-in-progress

xperimental · 2025-07-15T11:36:24Z

modules/logging-release-notes-6-3-0.adoc

+* With this release, default values of Splunk metadata keys: index, indexed fields, source, and message payload are predefined for log forwarders. The values are based on the log type. As a user, you can override these values. (https://issues.redhat.com/browse/LOG-6859[LOG-6859]) 
+
+=== Log storage
+* With this release, you can specify the S3 secret in the `forcepathstyle` field. Use this field to configure Loki to use either path style or virtual host style S3 URL. By default, {aws-short} endpoints use the virtual host style URL, equivalent to setting the `forcepathstyle` attribute to `false`. (https://issues.redhat.com/browse/LOG-7024?[LOG-7024])


The first sentence sounds a bit weird. Maybe something like this?

Suggested change

* With this release, you can specify the S3 secret in the `forcepathstyle` field. Use this field to configure Loki to use either path style or virtual host style S3 URL. By default, {aws-short} endpoints use the virtual host style URL, equivalent to setting the `forcepathstyle` attribute to `false`. (https://issues.redhat.com/browse/LOG-7024?[LOG-7024])

* With this release, you can use the `forcepathstyle` field in the S3 secret. Use this field to configure Loki to use either path style or virtual host style for the S3 access. By default, only {aws-short} endpoints use the virtual host style URL, while others use path-style. (https://issues.redhat.com/browse/LOG-7024?[LOG-7024])

brendan-daly-red-hat

As Ashwin needs to add more bug fixes, I'm closing my review.

I'm onboarding as a peer reviewer, so please wait for @skopacz1 to approve my review before you proceed with my suggested changes.

brendan-daly-red-hat · 2025-07-15T12:09:01Z

modules/logging-release-notes-6-3-0.adoc

+[id="openshift-logging-release-notes-6-3-0-enhancements_{context}"]
+== New features and enhancements
+
+=== Log Collection


Use sentence-style capitalization

Suggested change

=== Log Collection

=== Log collection

brendan-daly-red-hat · 2025-07-15T12:11:35Z

modules/logging-release-notes-6-3-0.adoc

+
+=== Log Collection
+
+* With this release, you can configure multiple {aws-first} outputs with distinct IAM roles in the `clusterLogForwarder` resource. (https://issues.redhat.com/browse/LOG-6790[LOG-6790])


Suggestion to define IAM, if applicable:

Suggested change

* With this release, you can configure multiple {aws-first} outputs with distinct IAM roles in the `clusterLogForwarder` resource. (https://issues.redhat.com/browse/LOG-6790[LOG-6790])

* With this release, you can configure multiple {aws-first} outputs with distinct identity and access management (IAM) roles in the `clusterLogForwarder` resource. (https://issues.redhat.com/browse/LOG-6790[LOG-6790])

brendan-daly-red-hat · 2025-07-15T12:24:08Z

modules/logging-release-notes-6-3-0.adoc

+
+* With this release, you can configure affinity rules to control collector scheduling. (https://issues.redhat.com/browse/LOG-6858[LOG-6858])
+
+* With this release, default values of Splunk metadata keys: index, indexed fields, source, and message payload are predefined for log forwarders. The values are based on the log type. As a user, you can override these values. (https://issues.redhat.com/browse/LOG-6859[LOG-6859]) 


Remove the colon:

Suggested change

* With this release, default values of Splunk metadata keys: index, indexed fields, source, and message payload are predefined for log forwarders. The values are based on the log type. As a user, you can override these values. (https://issues.redhat.com/browse/LOG-6859[LOG-6859])

* With this release, the default values of Splunk metadata keys (that is, index, indexed fields, source, and message payload) are predefined for log forwarders. The values are based on the log type. As a user, you can override these values. (https://issues.redhat.com/browse/LOG-6859[LOG-6859])

brendan-daly-red-hat · 2025-07-15T12:26:59Z

modules/logging-release-notes-6-3-0.adoc

+* With this release, default values of Splunk metadata keys: index, indexed fields, source, and message payload are predefined for log forwarders. The values are based on the log type. As a user, you can override these values. (https://issues.redhat.com/browse/LOG-6859[LOG-6859]) 
+
+=== Log storage
+* With this release, you can specify the S3 secret in the `forcepathstyle` field. Use this field to configure Loki to use either path style or virtual host style S3 URL. By default, {aws-short} endpoints use the virtual host style URL, equivalent to setting the `forcepathstyle` attribute to `false`. (https://issues.redhat.com/browse/LOG-7024?[LOG-7024])


Suggestion for clarity:

Suggested change

* With this release, you can specify the S3 secret in the `forcepathstyle` field. Use this field to configure Loki to use either path style or virtual host style S3 URL. By default, {aws-short} endpoints use the virtual host style URL, equivalent to setting the `forcepathstyle` attribute to `false`. (https://issues.redhat.com/browse/LOG-7024?[LOG-7024])

* With this release, you can specify the S3 secret in the `forcepathstyle` field. Use this field to configure the Loki Operator to use either the path style or the virtual host style S3 URL. By default, {aws-short} endpoints use the virtual host style URL, which is equivalent to setting the `forcepathstyle` attribute to `false`. (https://issues.redhat.com/browse/LOG-7024?[LOG-7024])

brendan-daly-red-hat · 2025-07-15T12:38:57Z

modules/logging-release-notes-6-3-0.adoc

+* Before this update, alerting rules created by the {loki-op} incorrectly used the `message` field to display the message related to the alert. With this update, the alerting rules correctly use the `description` field.
+(https://issues.redhat.com/browse/LOG-6380[LOG-6380]) 
+
+* Before this update, alerting rules were visible in unrelated namespaces due to lack of filtering based on the namespace in the Prometheus rules endpoint. As a consequence, user alerts were visible in unrelated namespaces. With this update, rule label filters have been added to the handler configuration, preventing alerts from being visible in unrelated namespaces. As a result, alert visibility is now restricted to the original namespace. (https://issues.redhat.com/browse/LOG-6148[LOG-6148])


Suggestions to avoid duplication:

Suggested change

* Before this update, alerting rules were visible in unrelated namespaces due to lack of filtering based on the namespace in the Prometheus rules endpoint. As a consequence, user alerts were visible in unrelated namespaces. With this update, rule label filters have been added to the handler configuration, preventing alerts from being visible in unrelated namespaces. As a result, alert visibility is now restricted to the original namespace. (https://issues.redhat.com/browse/LOG-6148[LOG-6148])

* Before this update, because of a lack of filtering based on the namespace in the Prometheus rules endpoint, user alerts were visible in unrelated namespaces. With this update, rule label filters have been added to the handler configuration. As a result, alert visibility is now restricted to the original namespace. (https://issues.redhat.com/browse/LOG-6148[LOG-6148])

nice suggestion, thanks, updated!

brendan-daly-red-hat · 2025-07-15T12:42:03Z

modules/logging-release-notes-6-3-0.adoc

+
+* Before this update, alerting rules were visible in unrelated namespaces due to lack of filtering based on the namespace in the Prometheus rules endpoint. As a consequence, user alerts were visible in unrelated namespaces. With this update, rule label filters have been added to the handler configuration, preventing alerts from being visible in unrelated namespaces. As a result, alert visibility is now restricted to the original namespace. (https://issues.redhat.com/browse/LOG-6148[LOG-6148])
+
+* Before this update, `ClusterLogForwarder` CR status updates failed due to an incorrect patching method. As a consequence, the {clo} failed to update objects, causing log data inconsistencies. With this release, `ClusterLogForwarder` CR status uses the `Patch()` method instead of the `Update()` method. As a result, the {clo} no longer fails to update the object, improving log forwarding stability. (https://issues.redhat.com/browse/LOG-6539[LOG-6539]) 


Suggestion for clarity:

Suggested change

* Before this update, `ClusterLogForwarder` CR status updates failed due to an incorrect patching method. As a consequence, the {clo} failed to update objects, causing log data inconsistencies. With this release, `ClusterLogForwarder` CR status uses the `Patch()` method instead of the `Update()` method. As a result, the {clo} no longer fails to update the object, improving log forwarding stability. (https://issues.redhat.com/browse/LOG-6539[LOG-6539])

* Before this update, `ClusterLogForwarder` CR status updates failed due to an incorrect patching method. As a consequence, the {clo} failed to update objects, which caused log data inconsistencies. With this release, `ClusterLogForwarder` CR status uses the `Patch()` method instead of the `Update()` method. As a result, the {clo} no longer fails to update the object, which improves log forwarding stability. (https://issues.redhat.com/browse/LOG-6539[LOG-6539])

skopacz1

This is sort of a weird situation where Brendan only did a half review, but all of his comments look good to me. If you're still making changes to the PR, I think this would still need another peer review though

brendan-daly-red-hat · 2025-07-15T14:55:04Z

/remove-label peer-review-needed
/remove-label peer-review-in-progress

theashiot · 2025-07-15T15:20:44Z

Thaks, @brendan-daly-red-hat and @skopacz1 for the review! Apologies for the trouble. I've now added the missing content. I agree that this needs to be reviewed again.

theashiot · 2025-07-15T15:20:58Z

/label peer-review-needed

kabirbhartiRH · 2025-07-16T01:57:38Z

Should below issues be added under known issues?
https://issues.redhat.com/browse/LOG-7311
https://issues.redhat.com/browse/LOG-7386
https://issues.redhat.com/browse/LOG-7375

theashiot · 2025-07-16T09:05:21Z

Thanks, @brendan-daly-red-hat and @skopacz1 for the wonderful review! I've made all the suggested changes.

best,
ashwin

briandooley · 2025-07-16T10:03:56Z

Should below issues be added under known issues? https://issues.redhat.com/browse/LOG-7311 https://issues.redhat.com/browse/LOG-7386 https://issues.redhat.com/browse/LOG-7375

These will be included in the next z-stream release.

anpingli · 2025-07-16T10:17:31Z

it is better to remove these bugs. these bugs had been released in Logging 6.2 z-stream.

LOG-6711 When forwarding logs with Otel data module, vector pod cannot forward ovn audit logs
LOG-6539 cluster-logging-operator: the object has been modified
LOG-6380 Alerting rules for log-storage contains summary and message annotation instead of summary and description annotation
LOG-6806 CLF errors out when dataModel is Otel and tuning config is empty
LOG-6987 Change Loki configuration to update memberlist ring when ingester becomes unhealthy
LOG-7028 [Logging 6.3] Parsing errors under Loki distributor for audit tenant when using Otel DataModel
LOG-7189 Syslog: merging data from 'message' to the root of log make log event inconsistent with ViaQ data model

anpingli · 2025-07-16T10:20:17Z

we should include this bug.
LOG-6148 Loki log based alerts for application tenant are not filtered by namespace on dev-console

theashiot · 2025-07-16T11:36:45Z

we should include this bug. LOG-6148 Loki log based alerts for application tenant are not filtered by namespace on dev-console

This one's mentioned: https://github.com/openshift/openshift-docs/pull/96021/files#diff-615a1a88d52eafeb9b7cd91143bb5ea4e065d568bdd0fefc3d17829423b7328fR42

theashiot · 2025-07-16T12:02:02Z

it is better to remove these bugs. these bugs had been released in Logging 6.2 z-stream.

LOG-6711 When forwarding logs with Otel data module, vector pod cannot forward ovn audit logs LOG-6539 cluster-logging-operator: the object has been modified LOG-6380 Alerting rules for log-storage contains summary and message annotation instead of summary and description annotation LOG-6806 CLF errors out when dataModel is Otel and tuning config is empty LOG-6987 Change Loki configuration to update memberlist ring when ingester becomes unhealthy LOG-7028 [Logging 6.3] Parsing errors under Loki distributor for audit tenant when using Otel DataModel LOG-7189 Syslog: merging data from 'message' to the root of log make log event inconsistent with ViaQ data model

I've commented these out. They are not visible in the output now: https://96021--ocpdocs-pr.netlify.app/openshift-logging/latest/about/logging-release-notes.html

openshift-ci · 2025-07-16T12:15:28Z

@theashiot: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

brendan-daly-red-hat · 2025-07-16T12:16:28Z

/remove-label peer-review-needed
/remove-label peer-review-in-progress
/label peer-review-done

theashiot · 2025-07-16T12:35:44Z

/label merge-review-needed

anpingli · 2025-07-16T12:38:43Z

/lgtm

openshift-ci-robot · 2025-07-16T12:46:00Z

@theashiot: This pull request references OBSDOCS-1860 which is a valid jira issue.

In response to this:

Version(s): 6.3

Issue: OBSDOCS-1860

Link to docs preview: https://96021--ocpdocs-pr.netlify.app/openshift-logging/latest/about/logging-release-notes.html

QE review:

QE has approved this change.

Additional information:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

theashiot · 2025-07-16T12:46:38Z

Thanks, @anpingli!!

gabriel-rh

/LGTM

gabriel-rh · 2025-07-16T12:59:23Z

/cherrypick standalone-logging-docs-6.3

openshift-cherrypick-robot · 2025-07-16T13:00:13Z

@gabriel-rh: new pull request created: #96170

In response to this:

/cherrypick standalone-logging-docs-6.3

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 11, 2025

openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 11, 2025

openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 11, 2025

theashiot force-pushed the OBSDOCS-1860 branch from 8d58a90 to 041b156 Compare July 11, 2025 17:28

theashiot force-pushed the OBSDOCS-1860 branch 2 times, most recently from a592b4b to 8ed6d77 Compare July 14, 2025 12:22

theashiot marked this pull request as ready for review July 14, 2025 12:23

openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 14, 2025

theashiot force-pushed the OBSDOCS-1860 branch from 8ed6d77 to 022d2fe Compare July 14, 2025 13:23

openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Jul 14, 2025

openshift-ci bot added the peer-review-in-progress Signifies that the peer review team is reviewing this PR label Jul 15, 2025

xperimental reviewed Jul 15, 2025

View reviewed changes

brendan-daly-red-hat reviewed Jul 15, 2025

View reviewed changes

theashiot force-pushed the OBSDOCS-1860 branch 2 times, most recently from 03342d1 to 78f33a4 Compare July 15, 2025 14:30

skopacz1 reviewed Jul 15, 2025

View reviewed changes

openshift-ci bot removed peer-review-needed Signifies that the peer review team needs to review this PR peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Jul 15, 2025

openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Jul 15, 2025

theashiot force-pushed the OBSDOCS-1860 branch from 78f33a4 to b9092c1 Compare July 16, 2025 09:04

OBSDOCS-1860: Release Notes (RNs) for OpenShift Logging 6.3 Release

1be71a6

theashiot force-pushed the OBSDOCS-1860 branch from b9092c1 to 1be71a6 Compare July 16, 2025 12:01

openshift-ci bot added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Jul 16, 2025

openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Jul 16, 2025

openshift-ci bot assigned anpingli Jul 16, 2025

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 16, 2025

gabriel-rh added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Jul 16, 2025

gabriel-rh approved these changes Jul 16, 2025

View reviewed changes

openshift-ci bot assigned gabriel-rh Jul 16, 2025

gabriel-rh merged commit 9bb0269 into openshift:standalone-logging-docs-main Jul 16, 2025
2 checks passed

openshift-cherrypick-robot mentioned this pull request Jul 16, 2025

[standalone-logging-docs-6.3] OBSDOCS-1860: Release Notes (RNs) for OpenShift Logging 6.3 Release #96170

Merged

	* With this release, you can specify the S3 secret in the `forcepathstyle` field. Use this field to configure Loki to use either path style or virtual host style S3 URL. By default, {aws-short} endpoints use the virtual host style URL, equivalent to setting the `forcepathstyle` attribute to `false`. (https://issues.redhat.com/browse/LOG-7024?[LOG-7024])
	* With this release, you can use the `forcepathstyle` field in the S3 secret. Use this field to configure Loki to use either path style or virtual host style for the S3 access. By default, only {aws-short} endpoints use the virtual host style URL, while others use path-style. (https://issues.redhat.com/browse/LOG-7024?[LOG-7024])


		=== Log Collection

		* With this release, you can configure multiple {aws-first} outputs with distinct IAM roles in the `clusterLogForwarder` resource. (https://issues.redhat.com/browse/LOG-6790[LOG-6790])


		* With this release, you can configure affinity rules to control collector scheduling. (https://issues.redhat.com/browse/LOG-6858[LOG-6858])

		* With this release, default values of Splunk metadata keys: index, indexed fields, source, and message payload are predefined for log forwarders. The values are based on the log type. As a user, you can override these values. (https://issues.redhat.com/browse/LOG-6859[LOG-6859])

	* With this release, default values of Splunk metadata keys: index, indexed fields, source, and message payload are predefined for log forwarders. The values are based on the log type. As a user, you can override these values. (https://issues.redhat.com/browse/LOG-6859[LOG-6859])
	* With this release, the default values of Splunk metadata keys (that is, index, indexed fields, source, and message payload) are predefined for log forwarders. The values are based on the log type. As a user, you can override these values. (https://issues.redhat.com/browse/LOG-6859[LOG-6859])


		* Before this update, alerting rules were visible in unrelated namespaces due to lack of filtering based on the namespace in the Prometheus rules endpoint. As a consequence, user alerts were visible in unrelated namespaces. With this update, rule label filters have been added to the handler configuration, preventing alerts from being visible in unrelated namespaces. As a result, alert visibility is now restricted to the original namespace. (https://issues.redhat.com/browse/LOG-6148[LOG-6148])

		* Before this update, `ClusterLogForwarder` CR status updates failed due to an incorrect patching method. As a consequence, the {clo} failed to update objects, causing log data inconsistencies. With this release, `ClusterLogForwarder` CR status uses the `Patch()` method instead of the `Update()` method. As a result, the {clo} no longer fails to update the object, improving log forwarding stability. (https://issues.redhat.com/browse/LOG-6539[LOG-6539])

OBSDOCS-1860: Release Notes (RNs) for OpenShift Logging 6.3 Release #96021

OBSDOCS-1860: Release Notes (RNs) for OpenShift Logging 6.3 Release #96021

Uh oh!

Conversation

theashiot commented Jul 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Jul 11, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci bot commented Jul 11, 2025

Uh oh!

theashiot commented Jul 11, 2025

Uh oh!

ocpdocs-previewbot commented Jul 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

theashiot commented Jul 11, 2025

Uh oh!

openshift-ci-robot commented Jul 11, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

theashiot commented Jul 14, 2025

Uh oh!

brendan-daly-red-hat commented Jul 15, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

brendan-daly-red-hat left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

skopacz1 left a comment

Choose a reason for hiding this comment

Uh oh!

brendan-daly-red-hat commented Jul 15, 2025

Uh oh!

theashiot commented Jul 15, 2025

Uh oh!

theashiot commented Jul 15, 2025

Uh oh!

kabirbhartiRH commented Jul 16, 2025

Uh oh!

theashiot commented Jul 16, 2025

Uh oh!

briandooley commented Jul 16, 2025

Uh oh!

anpingli commented Jul 16, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

anpingli commented Jul 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

theashiot commented Jul 16, 2025

Uh oh!

theashiot commented Jul 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

theashiot commented Jul 11, 2025 •

edited

Loading

openshift-ci-robot commented Jul 11, 2025 •

edited by openshift-ci bot

Loading

ocpdocs-previewbot commented Jul 11, 2025 •

edited

Loading

openshift-ci-robot commented Jul 11, 2025 •

edited by openshift-ci bot

Loading

anpingli commented Jul 16, 2025 •

edited by openshift-ci bot

Loading

anpingli commented Jul 16, 2025 •

edited

Loading

theashiot commented Jul 16, 2025 •

edited

Loading

openshift-ci-robot commented Jul 16, 2025 •

edited by openshift-ci bot

Loading